Integration Settings Tab

Use this tab to set values for integrations with other systems.

OB10

Field Description
Vendor No. Enter the OB10 vendor number. TrafficLIVE uses it for output that is compatible with OB10, an e-invoicing platform.

Sage

Field Description
Post invoices to Sage automatically? (Yes/No) Select Yes to have TrafficLIVE automatically send invoices to Sage with no further intervention from you.

You must enable integration with Sage before you can use this option.

Mailchimp

Field Description
Enable MailChimp Integration Select this check box to enable Mailchimp integration.
API Key Enter your unique API Key generated within MailChimp.

Maconomy

Field Description
Enable job + time sheet integration Select this check box to enable the integration of jobs and time sheets.
Enable expense sheet integration Select this check box to enable the integration of employee-submitted expenses.
Enable purchase order integration Select this check box to enable the integration of approved and issued purchase orders.
Enable Employee Sync Select this check box to enable the integration of internal staff information.
Enable Budget sync Select this check box to enable the functionality to synchronize budgets with TrafficLIVE. This option only works with Maconomy 2.2 and later.
Maconomy Budget type Use this field to specify the budgets in the Maconomy system that TrafficLIVE should use for integration.
Enable Absence sync Select this check box to enable the integration of approved staff absence requests.
Sign off imported absence Select this check box to enable the automatic sign-off of staff absence time sheets.
Company Number Enter your company's number. This is the number that Deltek provided as your company number when you set Maconomy up. It is typically three digits. If you have more than one company number in Maconomy, enter all of the company numbers that you are integrating with TrafficLIVE, separated by commas, such as 100,101,102.
Task Name Leave this field blank. It is not used in the integration.
Last Fetched Created Date, Last Fetched Closed Date Enter the dates for which the TrafficLIVE integration should search for new and closed jobs, respectively.
  • Last Fetched Created Date — Decide how far back in time you want the oldest job to be that you connect to TrafficLIVE. Set this date to capture all live jobs based on the date on which the earliest one was created in Maconomy.

  • Last Fetched Closed Date — TrafficLIVE scans Maconomy for closed jobs and reconciles them against TrafficLIVE. You typically set this to the same date as the last fetched created date.
Service User Enter the service user name that you obtained for Maconomy. Including a reference to TrafficLIVE in this name can help to clarify in Maconomy that this user is linked to the TrafficLIVE integration.

The service user must have access to your Maconomy company or companies, be able to submit and approve time sheets, and be able to access any data that is required by the integration functions that you are selecting.

Service Password Enter the password for the service user name. Maconomy passwords have an expiration date, so remember that you also need to manage this in TrafficLIVE or the integration stops working when the password expires.
URL Base Enter the URL of the Maconomy server. The TrafficLIVE support team coordinates with your IT department and Maconomy to obtain this URL.
REST URL Base Enter a second URL field to support additional integration features using the Maconomy REST API.
Maconomy Expense Sheet Approver Comment Property Enter Maconomy Expense sheet approver comment. The information must match equivalent fields in the expenses area of Maconomy to control the way the expenses synchronization works.
Maconomy Denied Expense Sheet Value Enter the Maconomy denied expense sheet value. The information must match equivalent fields in the expenses area of Maconomy to control the way the expenses synchronization works.
Maconomy Incurred Country Property Enter the Maconomy incurred country property. The information must match equivalent fields in the expenses area of Maconomy to control the way the expenses synchronization works.
Click after you have performed the initial synchronization of Maconomy jobs onto a "waiting list" from which you can select when synchronizing jobs between Maconomy and TrafficLIVE. This can take some time depending on data volume and the date range that you provided.
Click after checking for new jobs to update the waiting list of jobs and mark any synchronized jobs that are closed in Maconomy as closed in TrafficLIVE. This can take some time depending on the volume of data.

On the first synchronization, you might see a series of error messages. This occurs because the search returns results for closed jobs that might include jobs that were created outside of the job synchronization date that have not have been loaded into TrafficLIVE, and are therefore not recognized. You can ignore these error messages during the initial synchronization.

After the initial synchronization, use this button to synchronize closed jobs on a regular basis.

Click to update the status of expense records in TrafficLIVE, bringing them in line with the status of the linked records in Maconomy.
Click to update the status of purchase order records in TrafficLIVE, bringing them in line with the status of the linked records in Maconomy.
Use this button only when a complete replacement of the waiting list of Maconomy jobs is required in TrafficLIVE; this is typically when you change the Maconomy system with which you are synchronizing.
Compare Employees Click to produce a report of employees in both TrafficLIVE and Maconomy, which allows you to check both lists and look for irregularities.
Synchronize Absence Click to check in Maconomy for any approved absence requests and update your TrafficLIVE system accordingly.

Identity Access Management

You can configure TrafficLIVE to use SAML-2-based centralized authentication against major identity providers. This enables customers who already have a SAML-2-compatible identity provider to replace the TrafficLIVE login with their own authentication service.

TrafficLIVE supports all bindings that are compatible with the Web Browser SSO profile, for example, HTTP Redirect binding and HTTP POST binding. TrafficLIVE does not currently support SAML SOAP bindings.

Field Description
IAM Type Select the IAM type, either TRAFFIC_INTERNAL (default) or SAML.
SAML IdP Id Enter your identity provider's ID. This must be the same as the value of the entityID attribute in the following SAML IdP Metadata field.
SAML IdP Metadata Paste your identity provider's metadata into this text box.

Xero

Field Description
Enable Xero Integration Select this check box to enable Xero integration.
Consumer Key Enter the Consumer Key that Xero generated.

TrafficLIVE InMail

Field Description
Mail Sub Domain This field is not currently in use.